Data storage for multiple data types

ABSTRACT

There is provided an apparatus that includes an input address port to receive an input address from processor circuitry. Address storage stores a translation between the input address and an output address in an output address space. An output address port outputs the output address. An input data port receives data. Data storage stores the data. An output data port outputs the data stored in the data storage and control circuitry causes the data storage to store the translation between the input address and the output address. The control circuitry issues a signal to cause a page walk to occur in response to the input address being absent from the address storage and the data storage.

The present technique relates to data storage.

A data processing system often has a number of storage devices used forimproving performance of the overall system in which frequently accessedinformation, or information that would be time consuming to obtain, arestored for quick access. However, such storage devices are typicallylimited in size because of the circuit space they occupy, the cost ofthe hardware used to implement them or because the use of a largerdevices could increase the access time for all accesses to thathardware. However, in some instances, additional storage in such devicescould be advantageous and could provide a performance improvement.

Viewed from a first example configuration, there is provided an inputaddress port to receive an input address from processor circuitry;address storage to store a translation between the input address and anoutput address in an output address space; an output address port tooutput the output address; an input data port to receive data; datastorage to store the data in one of a plurality of locations; an outputdata port to output the data stored in the data storage; and controlcircuitry to cause the data storage to store the translation between theinput address and the output address, wherein the control circuitry isadapted to issue a signal to cause a page walk to occur in response tothe input address being absent from the address storage and the datastorage.

Viewed from a second example configuration, there is provided receivingan input address from processor circuitry; storing, in address storage,a translation between the input address and an output address in anoutput address space; receiving data; storing the data in data storage;causing the data storage to store the translation between the inputaddress and the output address; and in response to the input addressbeing absent from the address storage and the data storage, issuing asignal to cause a page walk to occur.

Viewed from a third example configuration, there is provided anapparatus comprising: means for receiving an input address fromprocessor circuitry; means for storing a translation between the inputaddress and an output address in an output address space; means forreceiving data; means for storing the data, wherein the means forstoring the data are made to store the translation between the inputaddress and the output address; and means for issuing a signal to causea page walk to occur in response to the input address being absent fromthe address storage and the data storage.

BRIEF DESCRIPTION OF THE DRAWINGS

The present technique will be described further, by way of example only,with reference to embodiments thereof as illustrated in the accompanyingdrawings, in which:

FIG. 1 illustrates an apparatus in accordance with some embodiments;

FIG. 2 illustrates an apparatus in accordance with some embodiments;

FIGS. 3A and 3B collectively demonstrate how different requests aredistributed by the CPU in accordance with some embodiments;

FIG. 4 illustrates a maintenance operation in accordance with someembodiments;

FIG. 5 illustrates a process of handling overlapping requests;

FIG. 6 illustrates a process of receiving a new maintenance operation inaccordance with some embodiments;

FIG. 7 illustrates the combining of maintenance operations in accordancewith some embodiments;

FIG. 8 illustrates the use of a fill queue in accordance with someembodiments;

FIG. 9 shows, in flowchart form, the process of consulting against thefill queue, in accordance with some embodiments;

FIG. 10A demonstrates a first process of performing a fill operation anda maintenance operation in accordance with some embodiments;

FIG. 10B demonstrates a second process of performing a fill operationand a maintenance operation in accordance with some embodiments;

FIG. 11 shows a process of performing an access request during amaintenance operation in accordance with some embodiments;

FIG. 12 illustrates an example apparatus in accordance with someembodiments;

FIG. 13 illustrates the reallocation of ways within a cache inaccordance with some embodiments;

FIG. 14 demonstrates how a single memory can be allocated to multiplepurposes using a pointer, in accordance with some embodiments;

FIG. 15 illustrates an example method of dynamically reallocating dataand address translations in accordance with some embodiments;

FIG. 16 shows how the use of different allocation policies alters thedistribution of cache ways in accordance with some embodiments;

FIG. 17A illustrates how a request for an address at a TLB is forwarded,in accordance with some embodiments;

FIG. 17B illustrates issuing a request for an address in parallel, inaccordance with some embodiments;

FIG. 17C demonstrates a process in which performing a translation of anaddress causes the translated address to be provided and the data to befetched, in accordance with some embodiments;

FIG. 18 illustrates a flowchart that shows a method of handling incomingrequests in accordance with some embodiments;

FIG. 19 schematically illustrates a data processing apparatus;

FIG. 20 schematically illustrates address translation circuitry and thestorage of translation data in a DRAM;

FIGS. 21 and 22 are schematic timing diagrams;

FIG. 23 is a schematic flowchart illustrating a method;

FIG. 24 schematically illustrates address translation circuitry;

FIG. 25 schematically illustrates a DRAM;

FIG. 26 schematically illustrates data storage in the DRAM of FIG. 25;

FIG. 27 schematically illustrates a key-value pair;

FIG. 28 schematically illustrates a hash generator;

FIG. 29 schematically illustrates write circuitry; and

FIGS. 30 and 31 are schematic flowcharts illustrating respectivemethods.

This description relates to a number of potentially orthogonaltechniques, which may be used together in any combination. FIG. 1illustrates an example apparatus 100 in which all the techniques to bediscussed below are used simultaneously. The apparatus includes aplurality of processors 105 a, 105 b . . . , each having a dedicatedTranslation Lookaside Buffer 110 a, 110 b, . . . for the translation ofan input address to an output address in an output space. Each processoris able to send maintenance operations, lookup operations, and filloperations to an interconnect 125 via one or more input ports 135. Eachof these operations relates to address storage 155 (which can act as atranslation data buffer) associated with the interconnect 125. Thelookup operations comprise an input or initial address for which anoutput address in an output space is to be provided. The fill operationsare used to provide such translations. Meanwhile, a maintenance queue145 stores the maintenance operations, which are performedasynchronously by the maintenance circuitry 150 on the address storage155 so that the processor 110 a need not wait for the maintenanceoperations to be performed. The address storage 155 may take the form ofcircuitry to access a further TLB, for which the translation data mayactually be stored in the memory 115 and which can also access thememory 115 for so-called page table walks to populate the addressstorage. The interconnect 125 provides a connection to a main memory 115via one or more output ports 140. The main memory is controlled via acontroller 120. Data read from or to be written to the main memory 115can be stored in a cache 160, which is associated with the interconnect125. By providing a cache, the processors 105 a, 105 b, . . . can accessdata from the memory 115 more quickly than if a request has to be sentout of the interconnect 125 and handled by the memory controller 120.Storage from the cache 160 can be ‘stolen’ (temporarily or otherwisereallocated) for use by the address storage 155 so that the amount ofstorage available for storing address translations can be increasedbeyond the capacity of the address storage itself 155. The management ofthe stolen storage, as well as the operation of the maintenance queue145, address storage 155, and cache 160 is handled by the controlcircuitry 130. The control circuitry can control the timing of pagetable walks and TLB accesses so that for a particular translationrequest from the TLB 110 a, the page table walk can be initiated beforecompletion of a TLB lookup. The controller 120 and the control circuitry130 can cooperate to oversee the storage in and retrieval from thememory 115 of translation data in the form of key-value pairs such thatin some examples multiple such pairs can be stored in a single row ofmemory cells (accessible by a row buffer (not shown) of the memory 115)of the memory 115. Note that the main memory 115 and the cache 160itself could be implemented by using DRAM.

Asynchronous Maintenance

FIG. 2 illustrates an example of an apparatus 200 in accordance withsome embodiments. This apparatus comprises a set of inputs ports 210,which provide lookup operations and maintenance operations (collectivelyreferred to as ‘requests’) to a control circuitry 240. Lookup operationshaving the input address (lookup requests) are passed to the lookupcircuitry 230, which could for instance take the form of a TranslationLookaside Buffer (TLB). In some embodiments, the TLB could be providedvia DRAM. Maintenance operations (maintenance requests) are passed to amaintenance queue 220. Such apparatus 200 may be used for providingasynchronous maintenance in a storage system and is provided as anexample of an apparatus 200 comprising an input port 210 to receive,from a requester, any one of: a lookup operation comprising an inputaddress, and a maintenance operation; maintenance queue circuitry 220 tostore a maintenance queue of at least one maintenance operation; andaddress storage 230 to store a translation between the input address andan output address in an output address space, wherein in response toreceiving the input address, the output address is provided independence on the maintenance queue; and in response to storing themaintenance operation, the maintenance queue circuitry causes anacknowledgement to be sent to the requester.

In such embodiments, the requester may take the form of a processor suchas a Central Processing Unit (CPU). Via the input port 210 of theapparatus 200, the requester is able to issue a lookup operationcomprising an input address. The requester can also issue a maintenancerequest via the input port 210. For example, the maintenance operationcould be directed towards the maintenance of entries in address storage230, which stores translations between input addresses and outputaddresses in an output address space. The output address in an outputaddress space could take the form of a physical address (PA) or anintermediate physical address (IPA). An IPA can be used to partiallytranslate between virtual address (VA) and physical address (PA), forexample.

Two further operations enable the apparatus 200 to asynchronouslyperform maintenance operations. Firstly, in response to a maintenanceoperation being received, the maintenance operation is stored and themaintenance queue circuitry 220 causes an acknowledgement to be sentback to the requester. This acknowledgement is sent immediately (e.g.without waiting for the maintenance operation to be completed).Consequently, the requester is not stalled or blocked until themaintenance operation is performed. However, since the maintenanceoperation is not performed straight away, it is necessary for theaddress storage 230 to inhibit stale data from being provided. In otherwords, the apparatus 200 must continue to behave as if the maintenanceoperation has been performed.

Secondly, in response to receiving an input address (i.e. an address tobe translated), the corresponding output address is provided independence on the queue maintained by the maintenance queue circuitry220. Again, this is necessary to prevent the return of data that wouldnot be returned if queued maintenance operations have been performed.Each of these processes is discussed in more detail with reference withFIGS. 3A and 3B, below.

The circuitry in FIG. 2 also provides an example of: control circuitry240 to scan the maintenance queue for a conflict with the input addressin response to receiving the input address, wherein the output addressis provided independence on the queue by returning a miss if there is aconflict and providing the output address otherwise.

A conflict can occur when the input address provided at the input port210 relates to an address that would be affected by a maintenanceoperation held in the maintenance queue 220. In other words, if themaintenance operations being held in the maintenance queue 220 had beenperformed, then a different result for the input address would be storedin the lookup circuitry 230. As a consequence of such a conflictoccurring, and in order to prevent stale data from being returned, a TLBmiss is provided in response to the input address. This will in turncause a page walk process to begin, during which the correct outputaddress is retrieved. If there is no conflict, then the output addresscan be provided.

FIG. 2 also shows an example of maintenance circuitry 250 to cause aselected maintenance operation to be performed from the maintenancequeue. There are a number of ways in which the maintenance circuitry 250could select a maintenance operation and to cause a selected maintenanceoperation to be performed from the queue maintained by the maintenancequeue circuitry 220. In some embodiments, the maintenance circuitry 250selects a maintenance operation to be performed when the lookupcircuitry 230 is otherwise unengaged. For example, if there is a periodof time for which no input address is received at the input ports 210,then the maintenance circuitry 250 could take advantage of this downtimein order to cause one or more of the maintenance operations to beperformed. In some embodiments, the maintenance circuitry 250 maycontinually cause maintenance operations to be selected from themaintenance queue 220 and performed until there are none left. In someembodiments, maintenance operations are scheduled to be performed if aperiod of time has elapsed since they were added to the maintenancequeue 220 or when the maintenance queue 220 is full. Other techniques ofqueue selection will be known to the skilled person.

FIG. 2 also illustrates an example of combine circuitry 260 to combine aplurality of entries in the maintenance queue based on one or moreconditions. Such a process is discussed in more detail with reference toFIG. 7.

FIGS. 3A and 3B collectively illustrate the process of handling anincoming lookup operation comprising the input address. As previouslymentioned, the corresponding output address in the output address space(e.g. a physical address space or a partial/intermediate address space)is provided in dependence on the maintenance queue. FIGS. 3A and 3B arediscussed simultaneously.

The process begins at step 300, where a lookup operation, e.g. from avirtual address to a physical address, is received. This occurs from arequester such as a CPU 310 being sent to lookup circuitry 230. This maytake the form of a TLB lookup. At a step 320 the lookup circuitry 230accesses and looks up the maintenance queue 220. It is then determined,at a step 330, whether there is a conflict in the maintenance queue 220with the TLB lookup. If the result from the maintenance queue 220 to thelookup circuitry 230 indicates that such a conflict exists, then at astep 340, the lookup circuitry 230 issues a TLB miss. This causes a pagewalk to occur, which in some embodiments is initiated either by the CPU310 or by a special circuit known as a page table walker, in order toretrieve the physical address. If, however, at step 330, the resultissued by the maintenance queue 220 to the lookup circuitry 230indicates that no conflict exists, then at step 350 it is determinedwhether there is a tag match. In parallel with checking whether there isa conflict, a lookup is performed at the TLB 230 in step 360 andrelevant entries then have tags checked in step 350. The tag matchprocess determines whether there is a corresponding output address giventhe input address in the lookup circuitry 230. In practice, thiscommonly occurs by matching a part of the input address (referred to asthe tag) with an entry in the lookup circuitry 230. If such a tag is notfound, then the process proceeds to step 340 where a TLB miss is issuedback to the CPU 310 or page walker circuit. Alternatively, if a matchingtag is found, then at step 370 the corresponding output address isprovided back to the CPU 310. As shown in FIG. 3A, when the CPU 310issues a maintenance operation, this is issued to the maintenance queue220. When, for example, the lookup circuitry 230 is otherwise idle, themaintenance queue 220 can select a maintenance operation to beperformed. This is then performed on the set of translations stored bythe lookup circuitry 230.

Note that an acknowledgement is sent by the maintenance queue 220 inresponse to the maintenance operation being issued by the CPU 310.Accordingly, the CPU 310 need not block or stall as a consequence ofissuing the maintenance operation and waiting for that maintenanceoperation to be performed. Instead, it is possible for the maintenanceoperation to be queued and then performed at a convenient time. Thesefigures therefore provide an example of a method comprising receiving300, from a requester, any one of: a lookup operation comprising aninput address, and a maintenance operation; storing a maintenance queue220 of at least one maintenance operation; and storing a translationbetween the input address and an output address in an output addressspace, wherein in response to receiving the input address, the outputaddress is provided in dependence on the maintenance queue 330; and inresponse to storing the maintenance operation, causing anacknowledgement to be sent to the requester.

FIG. 4 illustrates a maintenance operation in accordance with someembodiments. In particular, FIG. 4 illustrates an example in which themaintenance operation accesses a plurality of translations in theaddress storage 230. FIG. 4 also illustrates an example in which themaintenance operation sequentially accesses translations in the addressstorage 230 and an example in which the address storage is adapted to bememory mapped; and the maintenance operation accesses translations inthe address storage 230 using non-temporal accesses.

A non-temporal access is one in which a new entry is not installed in acache as a consequence of that access. For example, as a result of thenon-temporal accesses, no entry is stored in the Last Level Cache (LLC).Such an action avoids adding unnecessary data to the cache as aconsequence of a maintenance operation. There is therefore an assumptionthat the data is not going to be used again in the near future and soshould not evict other useful data (and should not be cached). In someembodiments, rather than using a non-temporal access, a regular accessis used and any resulting entry added to the cache is given a highreplacement priority such that the entry will be replaced more easily.

FIG. 4 illustrates an example in which the maintenance operation is aninvalidation operation. In some embodiments, an invalidation operationcauses the valid flag of one or more entries in the table is made (e.g.cleared) to indicate that the entry is no longer usable. Accordingly,those entries can be replaced by other entries as required. In someother embodiments, the invalidation operation could cause entries to bedeleted altogether.

FIG. 4 also illustrates an example in which the invalidation operationis to invalidate one or more translations in the address storage 230based on one or more of: a virtual address, a range of virtualaddresses, an address space identifier, a virtual machine identifier, anintermediate physical address, and a physical address. The invalidationcould therefore use one or more (any combination) of such parameters inorder to indicate those entries that should be subject to theinvalidation. In some embodiments, other parameters could be used inaddition (or instead).

In this specific example, the invalidation operation is to invalidateentries where the address space identifier (ASID) or the virtual machineidentifier (VMID) is 1. This is achieved by scanning through each entryin the address storage, checking the value of ASID and VMID for anyentry that is equal to 1. Where such an entry is found, the valid flagfor that entry is cleared to indicate that the entry is no longer valid.In the example of FIG. 4, this is achieved by setting the valid flag tozero (invalid). It will be appreciated that invalidation operations canbe performed based on other fields. Note that the field need not be inthe table itself but could be associated with an entry in the table viaanother table, register, or flag. The address space identifier and thevirtual machine identifier are both techniques that are used in order todivide up entries of the table into groups. In particular, a virtualmachine identifier (VMID) may be used to identify entries that belong toa particular virtual machine instance in a system having a number ofvirtual machines. Similarly, address space may be segmented into anumber of sections with each section having its own identifier. Thesetechniques can even be combined so that each virtual machine canseparate its available memory into a number of different segments independence on that virtual machine. For example, each address spacecould be allocated to a different application running on a particularvirtual machine instance. In this way, each entry in the address storage230 can be associated with a particular purpose. An invalidationoperation can therefore be targeted at addresses associated with aparticular purpose. For example, an invalidation operation could beperformed in respect of all addresses associated with a particularapplication running on a particular virtual machine when, for instance,that application terminates. Similarly, an invalidation operation couldbe targeted based on simply a virtual machine identifier, if thatvirtual machine were to be terminated for instance.

It will be appreciated from the above paragraphs that the maintenanceoperation can be time consuming. Accordingly, by using the apparatus 200described with reference to FIGS. 2, 3A and 3B, it is possible toasynchronously perform maintenance such that a requester such as a CPUneed not be blocked or stalled while the maintenance operation isperformed. It is particularly important when the storage on which themaintenance operations are being performed is particularly large. Sincethe maintenance operations are not performed immediately, it isnecessary to resolve conflict that can occur between lookups and thequeued maintenance operations. This can be achieved by testing for suchconflict, and where a conflict is detected, causing the original data tobe retrieved (e.g. by issuing a TLB miss causing a page walk to beperformed). In this way, a queue of maintenance operations can bemaintained, and performed when appropriate.

Improving Asynchronous Maintenance Efficiency by SimultaneouslyPerforming Multiple Maintenance Operations

FIG. 4 illustrates an example in which the selected maintenanceoperation comprises scanning through at least some of the addressstorage 230 and performing an action in response to a condition beingmet; during the scanning, the maintenance circuitry 250 performs afurther action in response to a further condition being met; and thefurther action and the further condition correspond with a furthermaintenance operation to be performed from the maintenance queue.

In this particular example, it can be considered that a firstmaintenance operation exists for invalidating where an ASID is 1. Theremay be a second maintenance operation to perform invalidation where theVMID is 1. Rather than performing a first scan through each of theentries in the lookup circuitry 230 for entries where an ASID is 1, thenperforming a second scan through each of the entries of the lookupcircuitry 230 for where the VMID is 1. A single scan can be performedwhere each entry is checked to determine whether its value of ASID orVMID is 1. In this way, only a single scan through the entries of thelookup circuitry 230 is required and this can be used to reduce theoverhead of the maintenance operations. Accordingly, multiplemaintenance operations can be performed more efficiently. It will beappreciated that the action and the further action could be the same.Similarly, the condition and the further condition could also be thesame.

Improving Asynchronous Maintenance Efficiency by Recognising Reuse ofASID or VMID

FIG. 5 illustrates an example in which in response to the input addressrelating to an entry in the address storage 230 that has an overlap withan overlapping maintenance operation in the maintenance queue, theapparatus 200 is adapted to prioritise the overlapping maintenanceoperation.

When a particular application or virtual machine ends, the TLB entrieshaving an ASID value associated with that application, or VMID valueassociated with that virtual machine must be invalidated. If requestsfor the same ASID/VMID start to get received, it means that the TLB willhave to be filled with new entries. However, this cannot happen beforethe maintenance operation is performed. Hence, when a lookup operation(e.g. a translation request) overlaps with such a maintenance operation,it may be desirable to promote the maintenance operation.

FIG. 5 illustrates a flowchart that is similar to the flowchartpresented in FIG. 3B, which has been adjusted for this improvement. Theprocess proceeds as described in relation to FIG. 3B. However, at step330, if a maintenance conflict is detected, then at step 500 it isdetermined whether the maintenance operation that the conflict occurswith is an invalidation directed towards a particular ASID or VMID. Ifnot, then the process proceeds to step 340 as before where a TLB miss isissued. Otherwise, at step 510 the maintenance operations priority ispromoted. This causes the maintenance operation to be performed morequickly. In some embodiments, the priority of the maintenance operationis promoted to a highest level so that it is the next maintenanceoperation to be performed. The process then proceeds to step 340 where aTLB miss is performed, thereby resulting in a page walk.

Improving Asynchronous Maintenance Efficiency by Responding to a FullMaintenance Queue

The flowchart in FIG. 6 relates to examples in which in response toreceiving the maintenance operation when the maintenance queue is full,the maintenance circuitry is adapted to perform the selected maintenanceoperation. In particular, FIG. 6 relates to examples in which theselection is based on a maintenance operation in the maintenance queuethat will take the least time to be performed.

In some instances, a maintenance operation may be received when thequeue of maintenance operations 220 is already full. In such a case, therequester could be blocked or stalled until such time as the space isavailable within the queue 220. One way to handle this is for themaintenance circuitry 250 to immediately perform one of the maintenanceoperations held in the maintenance queue 220 for instance, in someembodiments, the maintenance circuitry 250 selects the fastestmaintenance operation from the maintenance queue 220 to be performed andimmediately performs that operation. For example, as shown in FIG. 6 atstep 600, a maintenance operation is received. At step 610 it isdetermined whether the maintenance queue 220 is full or not. If not,then the process proceeds to step 670 where the new maintenanceoperation is added to the queue. Otherwise, at step 620, a loop beginsin which the next maintenance operation of the maintenance operationsheld within the maintenance queue 220 is fetched. At step 630 it isdetermined whether this maintenance operation is faster than the fastestmaintenance operation that has been determined so far. As a default, ifno maintenance operation has yet been examined, then this will be true.In any event, if this condition is met, then at step 640 the currentmaintenance operation that is being examined is set as the currentfastest operation. The process then proceeds to step 650 if the currentmaintenance operation being examined is not faster at step 630 then theprocess proceeds directly to step 650. At step 650 it is determinedwhether there are more maintenance operations to be examined from themaintenance queue 220. If so, then the process proceeds back to step 620where the next maintenance operation is fetched. Otherwise, at step 660,the current fastest operation is performed. The newly receivedmaintenance operation that was received in step 600 is then added to themaintenance queue 220 at step 670.

Improving Asynchronous Maintenance Efficiency by Combining MaintenanceOperations

FIG. 7 illustrates an example of combine circuitry 260 to combine aplurality of entries in the maintenance queue based on one or moreconditions. For example, in some embodiments, the combine circuitry 260combines adjacent addresses in the address storage 230. For example,entries that relate to the same ASID and VMID where the address isadjacent. In this manner, the queue of maintenance operations can becompacted by replacing a plurality of entries that relate to adjacentaddresses with a single entry relating to a range of addresses.

In some embodiments, the one or more conditions include: (i) overlappingor adjacent VA/IPA regions can be merged; (ii) invalidate by VA issubsumed by an overlapping invalidate by ASID if the VA belongs to theASID; (iii) invalidate by IPA is subsumed by an overlapping invalidateby VMID if the IPA belongs to the VMID; and (iv) invalidate by ASID issubsumed by an invalidate by VMID if the ASID belongs to the VMID. Theseconditions are based on the relationship that a VA has an associatedASID, that an ASID has an associated VMID, and that an IPA has anassociated VMID.

Considering the example of FIG. 7, the queue initially has fiveoperations. The first two operations can be merged into a singleoperation, because they relate to the same ASID (1) and the same VMID(1) and the addresses are adjacent (0x1121 is adjacent to 0x1122).Condition (i) therefore applies. These operations can therefore bereplaced by a single invalidation operation, which is directed toinvalidate the addresses within the range 0x1121 to 0x1122 where theASID is 1 and the VMID is 1. Similarly, the next two operations of theinitial maintenance operation queue are also directed to the same ASID(2) and VMID (1) and also relates to adjacent addresses (0x009D isadjacent to 0x009E). Accordingly, these can be compacted in order toproduce a single maintenance operation to invalidate the range 0x009D to0x009E for an ASID of 2 and a VMID of 1. Accordingly, the compactedmaintenance queue has three entries. In this example, each of themaintenance operations associated with a priority. In this example, thepriority of the new entry is equal to the highest of the priorities ofthe maintenance operations that were combined. In this way, amaintenance operation does not decrease in priority as a consequence ofbeing combined with other operations. In other embodiments, the prioritycould be averaged between all of the operations that make up the newoperation. It will be appreciated that other options are available andwill be known to the skilled person.

Accordingly, it can be seen that the maintenance queue 220 can becompacted, thereby allowing further maintenance operations to be addedto the maintenance queue 220 without the requester having to be stalledor blocked. The compacting process does not cause any maintenanceoperation to be lost. The combining process merely amalgamates entriestogether.

Improving Asynchronous Maintenance Efficiency by Use of a Fill Queue

FIG. 8 illustrates an example of fill queue circuitry 800 to store atleast one fill operation for a new translation in the address storage230, wherein the input port 210 is adapted to receive the filloperation; and in response to the fill operation having at least someoverlap with an overlapping maintenance operation in the maintenancequeue, the fill queue circuitry 800 stores the fill operation, and ifthe fill operation fully overlaps the maintenance operation, themaintenance operation is removed from the maintenance queue, otherwise apriority of the overlapping maintenance operation is increased.

When a new entry is to be added to the address storage 230, for instancewhen a page table walk has occurred, there may be a conflict with apending maintenance operation. One example of where this could occur iswhere a maintenance operation is directed to perform an invalidateaccording to a particular ASID followed by a fill which will fill in aspecific mapping. In another example, an invalidate according to aparticular VA and a fill for the same VA could be issued at similartimes. In this case, the invalidate can be dropped and the entries canbe filled in directly.

By providing a fill queue 800 into which the fill operation can bestored, the fill operation can be delayed until such time as theconflicting maintenance operation is handled. In order to cause themaintenance operation that is conflicting to be resolved more quickly, apriority of the conflicting (i.e. overlapping) maintenance operation canbe increased. As shown in FIG. 8, when a fill operation is received, itis initially sent to the fill queue 800. Where the lookup circuitry 230takes the form of a TLB, the fill queue 800 could itself take the formof a smaller TLB. Here, consultation occurs with the maintenance queuein order to determine whether the operation can proceed directly to thelookup circuitry 230 or whether the operation must be held at the fillqueue 800. The process of making this determination is shown in moredetail with respect to FIG. 9. Once the conflicting maintenanceoperations have been completed, any entries that conflicted with thatmaintenance operation are promoted from the fill queue 800 to the lookupcircuitry 230. Similarly, maintenance operations entering themaintenance queue 220 consult with the fill queue 800 in order to ensurethat existing fill operations are effected by the maintenance operation.In some embodiments, the maintenance operation may not be able toproceed until such time as the fill operation has been performed.Similarly, when an input address is provided as part of a lookupoperation, this may be checked against the fill queue 800 as well as thelookup circuitry 230.

FIG. 9 illustrates an example of the consultation process that occursfrom the fill queue 800 for instance, the maintenance queue 220. At astep 900, a fill operation is received. At step 910, the maintenancequeue 220 is consulted. At step 920, it is determined whether there isan overlap between any of the entries in the maintenance queue and thefill operation. For example, it may be determined whether any of themaintenance operations have the potential to affect the fill operationthat has been received. If no such overlap exists, then at step 930 thefill operation is performed. This causes one or more entries of thelookup circuitry 230 to be updated. The process then proceeds back tostep 900. Alternatively, if an overlap is detected then the filloperation is added to the fill queue 800 and the priority of theconflicting maintenance operation is increased at step 940. Again, theprocess then returns to step 900. This process is illustrated in FIG.10A in which a maintenance operation is performed followed by the filloperation. In this example, it is assumed that the maintenance operationdoes not result in any of the entries in the address storage 230 beingaffected. However, having performed the maintenance operation, the filloperation, which is subsequently performed, results in the addition of anew entry shown in bold.

FIG. 10A therefore illustrates an example whereby in response to theoverlapping maintenance operation being completed (e.g. as part of theentries being scanned), the fill operation is performed on the addressstorage 230. As an alternative, FIG. 10B illustrates an example in whichthe fill operation is performed on the address storage 230 as themaintenance operation is performed. In particular, the maintenanceoperation scans through the entries of the address storage 230. Afterperforming the maintenance operation on the location at which the filloperation would cause a new entry to be inserted, the fill operation isperformed, thereby inserting the new entry. The remainder of themaintenance operation can then be performed on the remaining entries. Inthis way, the maintenance operation does not affect the fill operation,since the fill operation occurs after the maintenance operation hasaffected the entry at which the fill operation will occur. This approachbenefits from the principal of locality in that multiple operations areperformed on the same space in storage at the same time. This can avoidthe need to rescan through each of the entries of the address storage230 in order to locate the entry at which the fill operation will beperformed.

Improving Asynchronous Maintenance Efficiency by Allowing RequestsMid-Maintenance

FIG. 11 provides an example in which the selected maintenance operationcomprises scanning through at least some of the address storage 230 andperforming an action in response to a condition being met; and inresponse to receiving a fill operation relating to an input address, thefill operation is performed when the input address corresponds with apart of the address storage 230 that has already been scanned in respectof the selected maintenance operation.

Accordingly, while a maintenance operation is being performed it may bepossible to simultaneously permit an output address to be provided inresponse to an input address being input. In particular, the part of theaddress storage 230 that has already been subjected to the maintenanceoperation can be considered to be accessible, while the remainingportion of the address storage 230 is considered to be inaccessible. Inthis way, if an input address relates to an entry of the address storage230 which has already been scanned in respect of the selected ongoingmaintenance operation, then the corresponding output address can beprovided. Alternatively, if the input address relates to a part of theaddress storage 230 that has not been scanned in respect of the selectedmaintenance operation, or if the input address does not relate to any ofthe entries in the address storage 230, then a miss is provided back tothe requester. Accordingly, it is not necessary for the maintenanceoperation to complete in order for translations to be provided. Hence,instead of providing a miss, the result of the translation may beprovided. A counter 1000 is provided in order to track the point in theaddress storage 230 for which the maintenance operation has beenperformed. A comparator can be used in order to determine whether thepart of the address storage 230 that will be affected the lookupoperation or fill operation that has already been scanned by themaintenance operation.

FIGS. 2 and 11 therefore also provide an example of an apparatuscomprising: storage circuitry 230 to store a plurality of entries,wherein the storage circuitry 230 is adapted to perform a search for aselected entry by scanning at least some of the plurality of entries;reference circuitry 1000 to store an indication to a part of the storagecircuitry 230 that is still to be scanned as part of the search; andprocessing circuitry 240 to perform an operation that will affect one ofthe plurality of entries in response to said one of the plurality ofentries being absent from the part of the storage circuitry 230 that isstill to be scanned as part of the search as indicated by the referencecircuitry. In this case, the part of the storage circuitry 230 that isstill to be scanned is pointed to by the counter 1000, which is updatedduring the search. Note that in some embodiments, only a subset ofpossible entries is part of the search process, even from the beginning.For instance, where the storage circuitry 230 utilises a hash table,having determined approximately where the entry is located, only asubset of entries are to be searched in order to find the matchingentry. In this way, entries can be inserted into storage circuitry evenwhile a search is being performed, for instance.

Stealing Storage

FIG. 12 illustrates an apparatus 1200 in accordance with someembodiments in which a processor element 1220 provides input addressesto the input port 1210. The input address is provided to a TranslationLookaside Buffer (TLB) 1230, which stores a translation between theinput address and the output address in an output space. An outputaddress port 1240 allows the output address (or a further translation ofthe output address) to be output in order to access a memory 1290 atthat address. At the same time, the processor element 1220 is able toreceive data via an input data port 1250. In some embodiments (such asthe one shown in FIG. 12), the input data port is from the memory 1290to the apparatus 1200 so that when the memory 1290 is accessed, the dataat that location in memory 1290 is provided back to the apparatus. Thisdata can be stored in a cache 1260, e.g. backed by a DRAM. Finally,there is an output data port 1270 at which the data is output. In someembodiments, such as the one shown in FIG. 12, the data output port isprovided to enable the apparatus 1200 to output the data back to theprocessor element. Control circuitry 1280 is used to control the TLB1230 and the 1260. Furthermore, although the cache 1260 is used to storedata, it is also used to store some translations. In this way, the TLB1230 “steals” storage space from the cache 1260 to store translations,e.g. when the TLB 1230 is otherwise unable to store the translation.Note that there is no obligation for input data port 1250 and the outputdata port to be arranged in the manner they are. For example, the datacould be received from the processor element 1220 and output to thememory 1290. Indeed, data could be received and output in bothdirections as a consequence of data being both read from and written tomemory 1290. Furthermore, the various ports 1210, 1240, 1250, 1270 couldbe combined—either by combining the inputs ports 1210, 1250 together andthe output ports 1240, 1270 together, or by combining the processorports 1210, 1270 together and the memory ports 1240, 1250 together oreven combining all four ports 1210, 1240, 1250, 1270 together.

Consequently, FIG. 12 provides an example of an apparatus 1200comprising an input address port 1210 to receive an input address fromprocessor circuitry 1220; address storage 1230 to store a translationbetween the input address and the output address in an output addressspace; an output address port 1240 to output the output address; aninput data port 1250 to receive data; data storage 1260 to store thedata in one of a plurality of locations; an output data port 1270 tooutput the data stored in a data storage 1260; and control circuitry1280 to cause the data storage 1260 to store the translation between theinput address and the output address, wherein the control circuitry isadapted to issue a signal to cause a page walk to occur in response tothe input address being absent from the address storage and the datastorage.

In this manner, even though the amount of space available fortranslations can increase, the size of the address storage 1230 itselfremains unchanged. Consequently, the time taken to look up a translationin the address storage 1230 need not significantly change. Inparticular, if it is known that the translation is stored in the TLB1230 then little or no additional access time is required. This could beachieved by using, for instance, a predictor, that is used to speculateabout where the translation will be found. If the location is unknownthen access to the TLB 1230 and cache 1260 could be parallelised so thata translation is simultaneously looked up in both the address storage1230 and the data storage 1260. Again, this can greatly limit anyincreased lookup time required.

Similarly, the circuit size need not significantly increase as aconsequence of this change. In particular, since the size of the addressstorage 1230 remains unchanged, and since the translation is stored indata storage 1260 that might otherwise be expected to exist on such acircuit, the storage that is “stolen” in order to store the translationdoes not necessitate the addition of extra hardware. Consequently, theoverall circuit space of the apparatus 1200 need not increase. Hence, aperformance improvement can be achieved without the need for an increasein the circuit space. Note that FIG. 12 also provides an example inwhich the data storage 1260 and the address storage 1230 are separatememories. In particular, the Translation Lookaside Buffer (TLB) 1230 andthe data cache 1260 are separate devices on the data circuitry. In someembodiments, each of these devices could have their own individualcontrol circuitry instead of or as well as their own control circuitry1280. There is however no need for the data storage and the addressstorage to be separate memories. In particular, in some embodiments, theaddress storage 1230 and the data storage 1260 may be the same memoryand thereby pool the same area of memory for multiple purposes.

FIG. 13 shows an example in which the plurality of locations takes theform of an n-ways set-associative memory; and the control circuitry 1280is adapted to cause the data storage 1260 to store the translation inone or more repurposed ways of the n-ways. In a set-associative memory,there are a number of locations in which a piece of data may be stored.Each such location is referred to as a “way”. This may arise, forinstance, as a consequence of the amount of storage in theset-associative memory being significantly less than the set of datathat is to be stored. By devising the memory in such a manner that thereare a number of ways, the flexibility of the memory can be increased.For example, a hash could be performed on the address to work out whichlocation it should be stored in. In case several pieces of data wish tobe stored in the same location, a number of ‘ways’ are provided so thata number of pieces of data can be stored at the same hash value. At oneextreme end, memory is ‘directly mapped’ in which case there is exactlyone location in which data can be stored. At the other extent, thememory is fully-associative, in which data can be stored anywhere. Inthe example of FIG. 13, n is 5, so the memory is 5-way associative.Consequently, for a given piece of data, there are five differentlocations that that data can be stored. Each way is also comprised of 11indexes (often referred to as sets) allowing 11 different pieces of datato be stored within each way. In the case of FIG. 13, two of the ways(shaded) have been repurposed such that they can be used by thetranslation lookaside buffer TLB 1230. Data that would ordinarily bestored in one of these repurposed ways, is instead allocated to one ofthe other ways.

Another way of enabling the data storage to be repurposed is by the useof addresses. FIG. 14 illustrates an example in which the plurality oflocations takes the form of an n-ways set-associative memory; and thecontrol circuitry 1280 is adapted to cause the data storage 1260 tostore the translation in one or more repurposed sets 1410 of the memory.In this example, a region pointer 1400 points to an address that marks aboundary between the translations that are stored by the address storage1230, and the data that is stored by the data storage 1260. In thisexample, the boundary is shown as moving, as sets within the datastorage 1260 are repurposed for storage of translations. Consequently,when an input (and output) address are provided by the processorcircuitry, to create a new translation, the translation can be stored inthis repurposed area. It will be appreciated that as the sets arerepurposed, a hash function that is used for indexing into the datastorage 1260 must adapt so that it no longer refers to non-repurposedsets. Meanwhile, the remaining sets 1420 of the data storage 1260 can beused for storing data. This boundary may be referenced, for instance, bya set index. In this way, FIG. 14 illustrates an example in which thedata storage 1260 and the address storage 1230 are different regionswithin the same memory. FIG. 14 therefore also provides an example of aregion pointer 1400 to indicate a border between a region used by theaddress storage 1410 and a region used by the data storage 1420. For thepurposes of the remainder of this description, although the terms‘address storage’ and ‘data storage’ will be used, this is not to beinterpreted as requiring separate memories. Furthermore, althoughexamples below may refer to a way, a storage location, or an address,the skilled person would appreciate that the use of repurposing ways orrepurposing sets are interchangeable techniques. FIG. 14 thereforeillustrates method comprising: receiving an input address from processorcircuitry; storing, in address storage 1230, a translation between theinput address and an output address in an output address space;receiving data; storing the data in data storage 1260; causing the datastorage 1260 to store the translation between the input address and theoutput address; and in response to the input address being absent fromthe address storage and the data storage, issuing a signal to cause apage walk to occur.

Stealing Storage Using Policies

FIG. 15 shows an example of a policy in accordance with someembodiments. In particular, FIG. 15 shows an example in which a policyindicates for each of the plurality of locations, a preference forstoring a translation compared to data. The policy is shown in the formof a flowchart 1500. At a step 1510, a new translation is received. Atstep 1520 a storage location w is determined based on the translation.This could be calculated based on performing a hash operation, such asperforming a modulus operation on the input address or the outputaddress that is the subject of the translation. At a step 1530, it isdetermined whether the current address miss rate is greater than a valuex for the storage location w 1560. In the example of FIG. 15, the valueof x for w is 5 out of 1000. Accordingly, if the address miss rate inthis case is greater than 5 for every 1000 instructions executed by theprocessor circuitry 1220, then the process proceeds to step 1540, wherethe translation is stored (e.g. in the data storage 1260). If not, thenat step 1550, it is determined whether the data miss rate is greaterthan a value y for the storage location w 1570. In this case, the valueis set at 30 out of 1000. Accordingly, if the data storage miss rate isgreater than 30 for every 1000 instructions executed by the processorcircuitry 1220, then the process proceeds to step 1540, where thetranslation is stored in the data storage 1260. Alternatively, theprocess proceeds to step 1555, where it is determined whether theaddress storage access rate is greater than a value z for the storagelocation w 1580. In this case, the value is set at 3 out of 4.Accordingly, if the access rate for the address storage is greater than3 out of 4 instructions executed by the processor circuitry 1220, thenthe process proceeds to step 1540, where the translation is stored inthe data storage 1260. Alternatively, the process proceeds back to 1510.In other words, the translation is not stored. In this example, thetranslation is stored in the data storage as a consequence of any ofthree conditions being met. The first is that the address miss rate isgreater than a first variable x. In this example, the value of x isgiven as 5 per 1000 instructions executed by the processor circuitry1220. However in another system, this value could be for example 10misses per 1000 instructions executed. A high address storage miss ratecan indicate an inefficiency occurring in the system. Accordingly, whenthe address storage miss rate reaches a certain point, it becomes moredesirable to store translations in order to increase the efficiency ofthe system. The second condition that can be met in order for thetranslation to be stored is that the data miss rate is above a variabley. In this example the variable y for the storage location w is equal to30 per 1000 instructions executed. However, in another system, thiscould be equal to 40 misses per 1000 instructions. A large number ofmisses with respect to the data storage indicates that there is poordata locality in the instructions being executed. Accordingly, the spacethat is ordinarily used for the storage of data may be better used byinstead storing translations. Hence, when the data storage rate reachesa certain point, it may be more desirable to store the translation. Thethird condition that can be met in order for the translation to bestored is that the address storage access rate is above a variable z. Inthis example, the variable z for the storage location w is equal to 3per 4 instructions executed. A large access rate indicates that therecould be contention for one of the storage devices, and it couldtherefore be desirable to spread the workload by storing data in thedata storage instead.

FIG. 15 also illustrates an example where the replacement policy isdynamically configurable. In particular, the values of x, y, and z for ware stored in registers 1560, 1270, and 1580, respectively. In this way,the preference for storing translations rather than data for the storagelocation w can be varied. It will of course be appreciated, that globalvalues for x, y, and z could also be set, which would be valid acrossall storage locations. FIG. 15 also provides an example of where thecontrol circuitry 1280 is adapted to cause the data storage 1260 tostore the translation between the input address and the output addressin dependence on at least one first condition. In particular, FIG. 15illustrates an example of where the first condition is from the listcomprising: a miss rate of the address storage 1230, a hit rate of theaddress storage 1230, an access rate of the address storage 1230, a missrate of the data storage 1260, a hit rate of the data storage 1260, andan access rate of the data storage 1260.

It will be appreciated that in some other embodiments, the conditions atsteps 1530, 1550, and 1555 could be inverted by testing for a value lessthan a predefined constant. In the case of the tests at steps 1530 and1550, the test could be for a value greater than a predefined constantrather than less than. Furthermore, in the case of the test at step1555, the access rate could consider the access rate of the datastorage. Other metrics could also be considered instead or as well. Forinstance, another metric that could be used is the number of misses,hits, or accesses in a number of clock cycles.

FIG. 16 provides an example in which the control circuitry 1280 isadapted to cause the translation between the input address and theoutput address to be stored in a part of the data storage 1260. In thisexample, the data storage 1260 is a cache. In particular, the datastorage 1260 is a 5-way associative cache, with each way comprising 11storage locations. The part of the data storage 1260 into which thetranslation is stored is shown in grey. In particular, it will be notedthat the number of ways differs for each storage location. For example,a first storage location 1650 has only a single way allocated for thestorage of the translation, as specified by a first indicator 1600,which considers a data storage miss rate and an address storage missrate at a time when a translation is considered for storage in thatlocation 1650. A second storage location 1660 has four ways allocated tothe storage of the translation as specified by a second indicator 1610,which again considers a data storage miss rate and an address storagemiss rate when a translation is considered for storage in that location1660. In this manner, FIG. 16 is an example of where a size of the partis dependent on at least one second condition. In particular, FIG. 16shows an example where the second condition is from the list comprising:a miss rate of the address storage 1230, a hit rate of the addressstorage 1230, an access rate of the address storage 1230, a miss rate ofthe data storage 1260, a hit rate of the data storage 1260, and anaccess rate of the data storage 1260. It will be appreciated that sincethe data storage miss rate and the address storage miss rate change overtime, different storage locations can end up with different amounts ofstorage allocated for translations. This provides flexibility so that ifa large number of translations occur at a time when the miss rates arehigh, then storage can be provided for those translations regardless ofwhere in memory they are to be placed.

Stealing Storage Access Processes

FIG. 17A illustrates an example of which in response to a miss on theinput address in the address storage 1230, a read request is sent to thedata storage 1260 for the translation. In particular, a request isreceived at the TLB 1230, from the processing circuitry 1220. Therequest comprises an input address for which the corresponding outputaddress is desired. If such translation is found at the TLB 1230, then a“hit” occurs, and the output address is forwarded back to the processingcircuitry 1220. If not, then a “miss” occurs, and the request isforwarded to the cache 1260, which in some embodiments is a Last LevelCache (LLC). Here, the part of the cache 1260 that is “stolen” for useby the TLB 1230 is searched for the input address. If a “hit” occurs,then the requested output address is forwarded back to the processingcircuitry 1220. Otherwise, a “miss” occurs, and due to the cache 1260being a LLC, this results in a page walk being performed. Note that inexamples where the TLB 1230 and the cache 1260 are a single memory, theforwarding may occur locally within the same circuitry. However, in suchsituations, two searches may still be performed—one on a first storagelocation used by the TLB 1230 and once on a secondary location primarilyused by the cache 1260. Alternatively, a single search may be performed.In each of these examples, if the search or searches have failed, then apage walk is performed by the processing circuitry 1220.

FIG. 17B illustrates an example in which the read request is sent to thedata storage 1260 in parallel with a page walk request being issued.Accordingly, in response to a miss occurring at the TLB 1230, a requestwill be forwarded to the cache 1260 and a page walk request willsimultaneously be issued by the processing circuitry 1220 to obtain theassociated output address. In this manner, if a page walk is necessary,it is not delayed by the additional searching of the cache 1260. This isbecause the page walk is performed simultaneously with the cache 1260being searched when the requested output address is found in either thecache 1260 or by performing a page walk it is immediately returned backto the processing circuitry 1220.

FIG. 17C illustrates an example in which in response to the outputaddress being determined based on an input address, the apparatus 1200is adapted to fetch data stored in the data storage 1260 that isassociated with the output address. When request is received by the TLB1230, if a hit occurs, then the corresponding output address isforwarded back to the processing circuitry 1220. At that point, a datarequest is made by the TLB 1230 to the cache 1260. If a hit occurs atthe cache 1260 then the data is returned to the processing circuitry1220. If there is a miss for the requested input address at the TLB1230, then the request is forwarded to the cache 1260. At that point, ifthere is a hit, then the output address is forwarded back to theprocessing circuitry 1220 and a data request is internally made at thecache 1260. Thereafter, if there is a hit for the data request, then thedata is forwarded back to the processing circuitry 1220. Accordingly,there is no need for the address to be forwarded back to the processorcircuitry 1220 for a subsequent data access request to be made by theprocessing circuitry 1220. Instead, the data can be returned, togetherwith the address, without necessarily involving the processing circuitry1220. This saves the time of an address being forwarded, the processingcircuitry 1220 issuing a data request, and the data request beingforwarded back to the cache 1260. Accordingly, data can be retrievedmore quickly. The skilled person will appreciate that misses are handledin the conventional manner.

FIG. 18 illustrates a flowchart 1800 that shows a method of handlingincoming requests in accordance with some embodiments. One way ofeffecting the stealing of the storage is to create a range of PA spacethat does not correspond to a backing storage (e.g. via a fake 10 deviceor a special read request to tell the cache controller to attempt toread an address and return a signal to indicate failure if the readcannot be completed). This mechanism could, for instance, be part of thecontrol circuitry 1280 or part of a controller for the TLB 1230 or cache1260. This makes it possible to mark a region of cacheable physicaladdress space as being suitable for storing address translations.However, because the range is unbacked, it does not actually storetranslations in backing storage (e.g. DRAM). In this way, the cache canbe made to “cache” translations that are believed to be stored inmemory, but are not. If the address provided as part of a request fallswithin the predefined range, then the request is a request for atranslation. While, ordinarily, a request for cacheable data that is notin the LLC would cause the data to be fetched from memory, such anoperation cannot be done in the case of the range of PA space that doesnot correspond to a backing store because, as stated above, this rangeis not actually backed by memory. Hence, when such a request isdetected, it is unable to directly fetch the data from memory. Instead,it issues a signal (e.g. to the control circuitry 1280) that causes apage walk to occur. In some embodiments, this causes the pagetranslations to be loaded from memory, and for the desired addresstranslation to be determined from those page translations.

The flowchart 1800 therefore begins at a step 1810 where a request isreceived. The request could be for an address translation or it could befor data. The request will therefore contain an address for which eitherdata or a translation is desired. At a step 1820, a lookup is performed.The lookup attempts to fulfil the request in one or more of the addressstorage 1230 and data storage 1260 as previously described. If thedesired information is located at step 1830 then the process returns tostep 1810 where the next request is received. Alternatively, the processproceeds to step 1840 where it is determined whether the request fallswithin the predefined range. If so, then at step 1850, a signal isissued that causes a page walk to occur. Alternatively, at step 1860,the data is loaded from memory. In either case, the process then returnsto step 1810. In this example, it is assumed that the predefined rangeis the address space that does not correspond to a backing store.However, in other embodiments, step 1840 could test whether the addressfalls outside the predefined range and the predefined address rangecould be defined by the address space that does correspond to a backingstore.

The flowchart 1800 therefore illustrates the behaviour of an apparatusin which in response to a request for the translation when thetranslation is absent from the address storage 1230 and the data storage1260, the control circuitry 1280 is adapted to issue a signal to cause apage walk to occur.

Timing of TLB Lookup and Page Table Walks

FIG. 19 schematically illustrates another example of a data processingapparatus comprising: one or more processing elements (PE) 1900, aninterconnect circuit 1910, a dynamic random access memory (DRAM) 1920and a DRAM controller 1930. This provides an example of data processingapparatus comprising: a memory 1920 accessible according to physicalmemory addresses; one or more processing elements 1900 to generatevirtual memory addresses for accessing the memory; and memory addresstranslation apparatus 1915 to provide a translation of the initialmemory addresses generated by the one or more processing elements tophysical memory addresses provided to the memory. In some examples,attributes such as page attributes, read, write and execute permissionscan also be obtained as part of the translation process and providedwith the output memory address. In example arrangements the one or moreprocessing elements 1900 each comprise a respective translationlookaside buffer 1905 to store a set of translation of the initialmemory addresses generated by that processing element to physical memoryaddresses provided to the memory; the translation lookaside buffer beingconfigured to request a translation not stored by the translationlookaside buffer from the memory address translation apparatus.

The arrangement of FIG. 19 is applicable to the various techniquesdiscussed with reference to FIGS. 20 to 31, either individually or incombination.

Each of the processing elements 1900 can access memory locations in theDRAM 1920. In principle this access could be directly via actual(physical) memory addresses. However, in order to provide partitioningand a degree of security between memory accesses by different processingelements (or in some cases different operating systems running on theprocessing elements 1900), the processing elements 1900 refer to memoryaddresses by so-called virtual or initial memory addresses. Theserequire translation into output or physical memory addresses to accessreal (physical) memory locations in the DRAM 1920.

A first level of translation can be performed by a so-called translationlookaside buffer (TLB) 1905 associated with each processing element. TheTLB 1905 stores or buffers recently-used translations between virtualmemory addresses and physical memory addresses, so that a virtual memoryaddress supplied to the TLB 1905 is translated to a physical memoryaddress which then forms part of a memory access to be DRAM 1920.However, the TLB has limited size and cannot store every single possiblememory address translation which may be called upon by the processingelement 1900. In the case that a required translation is not present inthe TLB 1905, the TLB refers to translation apparatus 1915, for exampleforming part of the interconnect circuitry 1910. The translationapparatus will be described in detail below and operates to provide orotherwise obtain the required translation and pass it back to the TLB1905 where it can be used to translate a virtual memory address into aphysical memory address.

Therefore, FIG. 19 provides an example of data processing apparatuscomprising:

a memory 1920 accessible according to physical memory addresses;

one or more processing elements 1900 to generate virtual memoryaddresses for accessing the memory; and

memory address translation apparatus 1915 to translate the virtualmemory addresses generated by the one or more processing elements tophysical memory addresses provided to the memory.

FIG. 20 shows the operation of the translation apparatus in more detail.

The translation apparatus 1915 maintains a so-called DRAM-backed TLB.That is to say, the translation apparatus 1915 maintains a buffersimilar to the TLB 1905 but generally rather larger, containingtranslation data, in the DRAM 1920 (shown schematically as a reserved orshaded portion 1921 of the DRAM 1920). Maintaining such a buffer in theDRAM 1920 allows the buffer to be relatively large because the DRAMcapacity, often off-chip relative to the processing elements 1900, istypically much larger than the typical on-chip static ram (SRAM) storageprovided for the local TLB 1905.

So, a first attempt to obtain a required translation requested by theTLB 1905 is for the translation apparatus 1915 to consult theDRAM-backed TLB data.

However, the DRAM-backed TLB also has a limited size, albeit ratherlarger than that of the local TLB 1905. In the case that data is notfound for a particular translation in the DRAM-backed TLB, a so-calledpage table walk process can be carried out. This involves consulting ahierarchy of so-called page tables also stored in DRAM which, together,provide a definitive set of all currently allowable memory addresstranslations.

The translation apparatus 1915 comprises control circuitry 2000 tocontrol a DRAM-backed access circuitry 2010 and a page table walk accesscircuitry 2020. Both of these consult respective portions of the DRAM1920 via the DRAM controller 1930 to obtain either an instance oftranslation data in the case of the DRAM-backed TLB access circuitry2010 or page table data from which the translation can be derived, inthe case of the page table walker access circuitry 2020. The controlcircuitry 2000 is therefore responsive to an input initial memoryaddress to be translated, to request retrieval of translation data forthe input initial memory address from the translation data buffer and,before completion of processing of the request for retrieval from thetranslation data buffer, to initiate retrieval of translation data forthe input initial memory address by the page table access circuitry.

The page table walk access circuitry 2020 is arranged to access pagetable data to retrieve translation data defining an address translationbetween an initial memory address in an initial memory address space,and a corresponding output memory address in an output address space.The DRAM-backed TLB is an example of a translation data buffer to store,for a subset of the virtual address space, one or more instances of thetranslation data.

As part of its operation, the DRAM-backed TLB access circuitry 2010provides a “valid” signal 2015 to the control circuitry 2000. Thecontrol circuitry 2000 provides control and, in some instances,cancellation (or at least cancellation initiation) signals 2005 to theDRAM-backed TLB access circuitry and the page table walk accesscircuitry 2020. This provides an example in which the translation databuffer is configured to respond to a request for retrieval of giventranslation data by providing a response comprising either the giventranslation data or data indicating that the given translation data isnot currently held by the translation data buffer.

Examples of the use of these signals will be discussed below.

Example arrangements provide variations of the timing of operation ofthe circuitries 2010, 2020 relative to previously proposed arrangements.To place these into context, FIG. 21 is a schematic timing diagramillustrating the operation of a previously proposed TLB and translationapparatus.

Four horizontal lines in FIG. 21 schematically illustrate operations bythe local TLB 1905, the DRAM-backed TLB access circuitry 2010, the pagetable walk access circuitry 2020 and the DRAM 1920 respectively. Timeruns from left to right as drawn.

An access to the DRAM-backed TLB is prompted by a required translationnot being found in the local TLB 1905 such that the local TLB 1905requests (at a stage 2100) the translation from the translationapparatus 1915. In the previously proposed arrangement, this causes theDRAM-backed TLB access circuitry 2010 to access (at a stage 2105) theDRAM to look up whether the required translation data is present. Theresponse from the DRAM 1920 is shown as a stage 2110. If there is a“hit”, which is to say the required instance of translation data isfound in the DRAM-backed TLB, then that translation data is returned tothe local TLB as a stage 2115 and the process terminates. If not, theDRAM-backed TLB access circuitry indicates to the control circuitry 2000that the requested instance of translation data is not available (by notsetting the “valid” signal, or by setting it to a state indicating “notvalid”) such that the control circuitry 2000 then issues a request 2120to the page table walk access circuitry 2020 to undertake a page tablewalk to obtain the required translation. Using established techniques, apage table walk involves multiple successive memory accesses 2125 inorder to access the required hierarchy of page tables to obtain atranslation. The result is the required translation provided at a stage2130, being ultimately transmitted at a stage 2135 to the local TLB 1905and the process terminates.

As shown by a stage 2160, but not forming part of the time-critical pathof FIG. 21, when the translation data for the input initial memoryaddress is not currently held by the translation data buffer, thecontrol circuitry is configured to store the translation data for theinput initial memory address, received from the page table accesscircuitry, in the translation data buffer in DRAM.

Because in the previously proposed example, the page table walk is notinitiated until the DRAM-backed TLB lookup has failed or missed, in theworst case there can be a long delay 2150 between the initial request at2100 by the local TLB 1905 and the local TLB 1905 receiving therequested translation data.

In contrast, FIG. 22 schematically illustrates an example arrangementaccording to examples of the present disclosure, in which the controlcircuitry is configured to request retrieval of a required instance oftranslation data from the DRAM-backed TLB and, before completion of theprocessing of that request for retrieval from the DRAM-backed TLB, toinitiate retrieval of the same translation data by the page table walkaccess circuitry 2010.

In some examples, the control circuitry can initiate both processessubstantially at the same time.

So, referring to FIG. 22, after the request 2100 by the local TLB 1905,the control circuitry 2000 initiates a DRAM-backed TLB lookup 2200 and,substantially at the same time, or at least before completion of thatTLB lookup, a page table walk 2205 by the page table walk accesscircuitry 2020. Both processes therefore proceed concurrently. This cansave latency in situations where a page table access is required, bystarting the page table access “early” rather than waiting until thetranslation data buffer access has failed.

Optional Early Termination of Page Table Access

If, however, there is a hit by the DRAM-backed TLB access circuitry2010, then optionally the page table walk can be terminated (illustratedschematically at a stage 2210). This is not a requirement and the pagetable walk could in fact be allowed to complete, in which case all thatwould happen is that the same translation data would be retrieved fromthe page table as well. However, by terminating the page table walk at2210 in the case of a TLB hit, a power saving (relating to the rest ofthe page table walk no longer taking place) can potentially be achieved.

In the case of a DRAM-backed TLB hit, the subsequent process is similarto FIG. 21 and the required instance of translation data is provided tothe local TLB at 2215.

If, however, there is a miss in the DRAM-backed TLB, then the page tablewalk continues at 2220 through to the provision at a stage 2225 of therequired translation derived from the page table walk to the local TLB1905. In this case, the overall latency or time period to provide thetranslation is shown as 2232 and there is a time saving shownschematically as a period 2230 over the arrangement shown in FIG. 21 byvirtue of starting the page table walk early, for example at the sametime as the DRAM-backed TLB lookup was started, or at least beforecompletion of the DRAM-backed TLB lookup.

Again, as shown by a stage 2260, but not forming part of thetime-critical path of FIG. 22, when the translation data for the inputinitial memory address is not currently held by the translation databuffer, the control circuitry is configured to store the translationdata for the input initial memory address, received from the page tableaccess circuitry, in the translation data buffer in DRAM.

FIG. 23 is a schematic flowchart illustrating a method appropriate tothe discussions above.

At a step 2300, page table data is accessed to retrieve translation datadefining an address translation between an initial memory address in aninitial memory address space and a corresponding output memory addressin an output address space.

Here, note that the initial memory address space could be a virtualmemory address space and the output memory address space could be aphysical memory address space. However, in some other arrangements, aso-called intermediate physical address is used, in some cases so as tohide the translation process or at least the full extent of thetranslation process, from individual operating systems so that an IPA toPA translation is carried out by a so-called hypervisor. The sameprinciples as those discussed here can relate to any of the following:VA to PA translation; VA to IPA translation; and/or IPA to PAtranslation.

Therefore, various embodiments are envisaged, all or any of which can beimplemented using these techniques, in which:

the initial memory address space is a virtual memory address space andthe output memory address space is a physical memory address space; or

the initial memory address space is an intermediate physical memoryaddress space and the output memory address space is a physical memoryaddress space; or

the initial memory address space is a virtual memory address space andthe output memory address space is an intermediate physical memoryaddress space.

In a multi-stage translation arrangement, these techniques could be usedfor one or more of the translation stages.

Referring back to FIG. 23, at a step 2310, for a subset of the initialmemory address space, one or more instances of the translation data arestored in a translation data buffer such as the DRAM-backed TLB.

At a step 2320, in response to an input initial memory address to betranslated, such as one received from the local TLB 1905, thetranslation data is requested for retrieval from the translation databuffer such as the DRAM-backed TLB.

Then, at a step 2330, before completion of processing of the request forretrieval from the translation data buffer, retrieval is initiated ofthe translation data for the input (required) initial memory address bypage table access circuitry such as the circuitry 2020 discussed above.

If, in fact, at a step 2340 the required data is successfully retrievedfrom the DRAM-backed TLB, then a step 2350, which is optional asdiscussed above, can involve initiating cancellation of the retrieval oftranslation data for the input initial memory address from the pagetable in response to the retrieval of the translation data for the inputinitial memory address from the translation data buffer such as theDRAM-backed TLB. This can in some instances save power by avoiding atleast a part of the page table access.

Otherwise, in instances where the data is not successfully retrievedfrom the DRAM-backed TLB, the required translation data is obtained bythe page table walk mechanism at a step 2360 and may be stored in theDRAM-backed TLB.

The steps 2320, 2330 are shown serially in FIG. 23, but in some examples(to provide a potentially improved overall latency saving where a pagetable access turns out to be needed) the control circuitry can beconfigured to initiate retrieval of translation data for the inputinitial memory address by the page table access circuitry substantiallysimultaneously with requesting retrieval of translation data for theinput initial memory address from the translation data buffer. In otherwords the steps 2320, 2330 can occur at substantially the same time. Inprinciple the step 2330 could even be initiated as the first of the twosteps. However, the broadest aspect of the example embodiments justenvisages starting the page table access before completion of thetranslation data buffer lookup, which can still achieve a saving inlatency.

Derivation of Predictions

Turning now to FIG. 24, in some examples, the control circuitry 2000 isconfigured to derive a prediction of whether the input initial memoryaddress is currently held by the translation data buffer. Ways in whichthis prediction can be derived and made use of will be discussed below.

In general terms, if a prediction is provided of whether the requiredtranslation is likely to be held by the DRAM-backed TLB, then it can bepossible to delay or avoid the page table lookup. In other examples, ifa prediction is provided that a page table access is likely to berequired, it can be possible to avoid or delay the DRAM-backed TLBlookup. Either of these instances can save power. If the prediction iswrong, however, they can introduce a latency penalty by returning theoverall latency of the system to a latency similar to that of FIG. 21.In other words, when the prediction indicates at least a first thresholdlikelihood that the input initial memory address is currently held bythe translation data buffer, the control circuitry is configured todefer initiating retrieval of translation data for the input initialmemory address by the page table access circuitry until a response isreceived from the translation data buffer. In other examples, when theprediction indicates less than a second threshold likelihood that theinput initial memory address is currently held by the translation databuffer, the control circuitry is configured to request retrieval oftranslation data for the input initial memory address from thetranslation data buffer for no more than a subset of instances of inputinitial memory addresses to be translated.

As mentioned earlier, the control circuitry 2000 controls the bufferlookup circuitry 2010 and the page table walk access circuitry 2020 toaccess data held by the DRAM 1920. The buffer lookup circuitry 2010provides an availability signal 2015 to the control circuitry 2000 toshow whether the DRAM-backed TLB lookup was successful or not. Inexample arrangements, that availability signal is also provided (in FIG.24) to one or more counters forming a counter circuitry 2400. Thecounter circuitry 2400 is arranged to detect, amongst responses by thetranslation data buffer, relative numbers of instances of a response forwhich the availability signal indicated that the response comprised therequested translation data and instances of a response comprising data(such as a negative availability indication 2015) indicating that therequested translation data is not currently held by the translation databuffer.

Therefore the control circuitry may comprise counter circuitry todetect, amongst responses by the translation data buffer, relativenumbers of instances of a response comprising the requested translationdata and instances of a response comprising data indicating that therequested translation data is not currently held by the translation databuffer.

In some examples, the counter circuitry 2400 comprises circuitry tochange a count value in one polarity (such as an increment) in responseto the translation data buffer providing the requested translation data(a positive availability signal 2015) and to change the count value inthe other polarity (such as a decrement) in response to the translationdata buffer not holding the data, which is to say the buffer lookupcircuitry 2010 providing data such as a negative availability indication2015 that the requested translation data is not currently held by thetranslation data buffer. Either one of opposite polarities may be usedin each case, and the increment amount and decrement amount could bedifferent to one another and need not be +/−1. In other words, themagnitude of an increment does not have to be the same as the magnitudeof a decrement.

A comparator 2410 compares the count values with first and secondthresholds THR1 and THR2. In some examples, the counter can be asaturating counter so that the count value is constrained not to gobeyond an upper count limit or below a lower count limit such as 0.

The counter circuitry 2400 can comprise one counter, or in otherexamples multiple counters to detect the relative numbers for one ormore categories of memory address transaction, so that the predictionmay be better matched to the categorisation of the current transaction.A list of example categories can comprise one or more selected from thelist consisting of:

-   -   a category indicating a virtual machine requesting the        translation (as indicated, for example, by a virtual machine        identifier forming part of the translation request);    -   a category indicating an initial address space amongst plural        initial address spaces (as indicated, for example, by an address        space identifier forming part of the translation request);    -   a category indicating a program counter of a processor        requesting the translation ((as indicated, for example, by a        program counter value forming part of the translation request);        and    -   a category indicating the initial address for which the        translation is requested.

One of the thresholds THR 1, THR 2 may be a value indicating a firstthreshold likelihood such as an upper threshold. When the prediction orcount value indicates at least the first threshold likelihood, this inturn indicates a likelihood that the input initial memory address iscurrently held by the translation data buffer, the control circuitry2000 is configured to defer initiating retrieval of translation data forthat input initial memory address by the page table walk accesscircuitry 2020 until a response is received from the translation databuffer. So, using this threshold, the operation can return to that shownschematically in FIG. 21. In instances where the prediction is correct,this saves power over the operations of FIG. 22. In instances where theprediction is wrong, the latency need be no worse than that of FIG. 21.The prediction is based upon at least an upper threshold occurring for acounted number of recent translation requests (either generally orglobally, or for a particular value of the category or categoriescovered by the multiple counters) having been met by the DRAM-backedTLB.

A second threshold likelihood, representing a lower likelihood that theinput initial memory address is currently held by the translation databuffer, is represented by a lower count value and—where the count, orthe relevant count, is less than the second threshold—this gives rise tothe control circuitry requesting retrieval of the translation data forthe input initial memory address from the translation data buffer for nomore than a subset of instances of input initial memory addresses to betranslated. In some examples, this can be no instances at all, but thiscould lead to difficulties in detecting an increased count or increasedlikelihood of the data being held by the DRAM-backed TLB, given that thelikelihood is determined by a count of successful TLB lookups. In otherwords, if the DRAM-backed TLB is no longer used when the count dropsbelow the lower threshold, this could give rise to a situation in whichthe likelihood of the DRAM-backed TLB holding the required translationcan never increase again. To address that potential problem, optionallya further counter 2420, counting up instances of translation data accessrepeatedly from 1 to N on a modulo N basis, where N is an integergreater than 1, can override by a signal 2430 the likelihood informationcoming from the comparator 2420 (for example, whenever it reaches N) toforce a DRAM-backed TLB lookup by the lookup circuitry 2010 (forexample, resetting the prediction mechanism as part of the sameoperation). In other words, the subset can be 1 in N instances of inputinitial memory addresses to be translated, where N is an integer greaterthan one.

Therefore, the use of the second threshold as discussed above providesan example of an arrangement in which, when the prediction indicatesless than the second threshold likelihood that the input initial memoryaddress is currently held by the translation data buffer, the controlcircuitry is configured not to request retrieval of translation data forthe input initial memory address from the translation data buffer.

Storage in the DRAM

FIG. 25 schematically illustrates aspects of an example arrangement ofthe DRAM 1920 of FIG. 19, providing an example of a dynamic randomaccess memory to provide the array of storage locations.

The DRAM 1920 comprises an array 2500 of storage locations 2505 arrangedin rows and columns, a row buffer 2510, a column multiplexer 2515 and arow decoder 2520. For DRAM, each storage location 2505 comprises a groupof bitcells, each bitcell comprising a capacitor which can beselectively charged or discharged to represent a 1 or 0 corresponding toone bit of the overall value represented by the corresponding storagelocation 2505.

Accesses to the DRAM 1920 are carried out in two stages. First, anactivation command specifying a row address 2525 is issued. The rowdecoder 2520 activates the corresponding row 2535, to bring theinformation stored in each of the storage locations 2505 of thecorresponding row into the row buffer 2510. Second, a column address2530 accompanies the actual read/write command, which controls thecolumn multiplexer 2515 to select an entry of the row buffer 2510corresponding to the specified column within the active row, and eitheroutput the information read from that entry as read data or update thedata in that entry based on write data provided with the write command.For a write operation, writes to the row buffer 2510 may be propagatedback to the corresponding storage location 2505 as well. Multipleread/write operations may be performed within the same active row,before the row is closed using a precharge command which closes theconnection between the row buffer 2510 and the active row 2535, ensuresthat the storage locations of the active row 2535 have been updated toreflect any writes to the row buffer 2510, and resets the row buffer2510 ready for another row to be selected as the active row.

Therefore, an example DRAM-backed translation data buffer as describedhere comprises: access circuitry (such as the row decoder) to access aselected row and to transfer information from the selected row to therow buffer. In example arrangements the dynamic random access memory isconfigured to read data in data bursts each of less than one row ofentries, and to transmit a part of the row buffer corresponding to a keyvalue. In general, in example arrangements, the DRAM is configured tocommunicate data in data bursts, and to only transmit the part of therow buffer corresponding to the provided key. Note that the term“bursts” describes how the DRAM communicates rather than how it readsdata from the data array. This technique can be used to output therequired data after a key has been matched.

FIG. 26 schematically illustrates the operation of a technique forretrieving translation data from the memory of FIG. 25, and inparticular from the row buffer 2510 which in this context has beenloaded with data retrieved from an active row 2535 of the memory fromFIG. 25 and comprises a plurality of entries to store information from arespective portion of a row of the memory array.

A key value 2600 depends upon at least the virtual memory address to betranslated. The row buffer contains multiple sets of key, value datasuch as a set 2610. Each key value in the row buffer K₁, K₂, K₃, K₄ isassociated with a respective value entry V₁, V₂, V₃, V₄. By deriving thenew key value 2600 using the same dependence upon the virtual memoryaddresses as the stored key values K₁ . . . K₄, comparison circuitry2620 can compare the key value 2600 with information stored in at leastone key entry K₁ . . . K₄ of the row buffer 2510, each key entry havingan associated value entry V₁ . . . V₄ for storing at least arepresentation of a corresponding output memory address. In this way,the comparison circuitry 2620 can identify which of the at least one keyentry, if any, is a matching key entry storing information matching thekey value 2600.

Circuitry 2634 combines the outputs 2632 of the four comparison circuits2620 into a format to control the operation of output circuitry 2630,which outputs one of the values entries V₁ . . . V₄ under control of thecomparison outputs 2632 as an output value 2640 so as to output, whenthere is a matching key entry, at least the representation of the outputmemory address in the value entry associated with the matching keyentry.

The value entry provides the required translation as discussed belowwith reference to FIG. 27.

Therefore, FIG. 26 taken in conjunction with FIGS. 19, 20 and 25provides an example of memory address translation apparatus 1915comprising: page table access circuitry 2020 to access a page table toretrieve translation data defining an address translation between aninitial memory address in an initial memory address space, and acorresponding output memory address in an output address space; atranslation data buffer 2010, 1920 to store, for a subset of the initialaddress space, one or more instances of the translation data; thetranslation data buffer comprising: an array of storage locations 2505arranged in rows and columns; a row buffer 2510 comprising a pluralityof entries 2610 each to store information from a respective portion of arow of the array; and comparison circuitry 2620 responsive to a keyvalue 2600 dependent upon at least the initial memory address, tocompare the key value with information stored in each of at least onekey entry K1-K4 of the row buffer, each key entry having an associatedvalue entry for storing at least a representation of a correspondingoutput memory address, and to identify which of the at least one keyentry, if any, is a matching key entry storing information matching thekey value; and output circuitry 2630 to output, when there is a matchingkey entry, at least the representation of the output memory address inthe value entry V1-V4 associated with the matching key entry K1-K4.

Example embodiments can provide an efficient mechanism for the accessingof translation data in a DRAM-backed translation data buffer using asingle memory access, such that a required row (which may be accessed bya hashed initial memory address or in dependence on an portion of theinitial memory address for example) is accessed, potentially as a singlememory access, and then the contents of that row are compared to a keyvalue dependent upon the initial memory address to detect whether thatrow contains the required translation. This can potentially reduce thelatency and memory traffic to retrieve the translation, as memoryaccesses to DRAM are potentially relatively slow so it can beadvantageous only to need one such access. By providing a key-valuearrangement for translation data stored in the memory row, multipletranslations can be stored in a row accessed by a single hashed (orother dependency) initial memory address, which can improve theefficiency of storage in the DRAM-backed translation data buffer. Inparticular, using a hashed or other dependency upon at least a portionof the initial memory address can allow a memory row to be effectivelyreserved for the initial memory address. In example arrangements theindex for the DRAM row is a hash (or part of) (VFN, VMID, ASID) and thesame goes for the key. The combination of DRAM row and key should be aunique to a specific tuple (VFN, VMID, ASID). The example of a hashedvalue allows the distribution of memory rows relative to initial memoryaddresses to be randomised (or pseudo-randomised). If the memory row isfull (because potentially other initial memory addresses can also pointthere) and a new translation needs to be stored (for example when thetranslation data for the input virtual memory address is not currentlyheld by the translation data buffer, so that the control circuitry isconfigured to store the translation data for the input virtual memoryaddress, received from the page table access circuitry, in thetranslation data buffer) then a victim deletion circuitry can be used toselect a key entry and associated value entry in the selected row foroverwriting (for example, a replacement policy based on informationstored in the row itself or in a different memory or memory region underthe control of the memory controller) in response to a detection by thedetector circuitry that the selected row has insufficient unusedcapacity to store the translation data (for example, using the samehashing/dependency to select a row as in the reading operation, therebyproviding unused key and value entries and value entries in the selectedrow. Example selection criteria can comprise one or more selected fromthe list consisting of least recently accessed key value and matchingentry; a random or pseudorandom selection of a key value and matchingentry; a not most recently accessed key value and matching entry; and afirst-in-first-out selection for the selected row.

In example arrangements, the key value can be dependent upon one or moreselected from the list consisting of: data indicating a virtual machinerequesting the translation; data indicating an initial address spaceamongst plural virtual address spaces; and data indicating the initialaddress for which the translation is requested. Therefore, using thesetechniques the key value can define the required translation provided bythe associated value.

FIG. 27 schematically illustrates a key, value pair, in which the keycomprises a concatenation of at least a part of a virtual machineidentifier (VMID), an address space identifier (ASID), a virtual framenumber (VFN) defining the initial memory address at least to aresolution of a frame or page size, and the value comprises in thisexample a concatenation of a physical frame number defining the outputaddress at least to the resolution of a frame or page size and also inthese examples one or more attributes defining read/write/execute orother example permissions or the like associated with the translation.Therefore, the key value is, in example embodiments, dependent upon oneor more selected from the list consisting of: data indicating a virtualmachine requesting the translation; data indicating a virtual addressspace amongst plural virtual address spaces; and data indicating thevirtual address for which translation is required.

Example data sizes for these fields are as follows:

Field Size (bits) Key, value sizes VMID 16 Key 68 ASID 16 VFN 36 PFN 36Value 60 Attr 24 Total 128 128

Therefore, each key-value pair occupies in (for example) 16 bytes,allowing four such pairs to be stored in an example 64-byte memory row.

In terms of selecting a row of the array of memory locations, aso-called hash generator 2800 (FIG. 28) can be used, so that thetranslation data buffer comprises row selection circuitry to select arow of the array in dependence upon a portion of the initial memoryaddress; and access circuitry (2520, FIG. 25) to access the selected rowand to transfer information from the selected row to the row buffer2510. In the particular example given, the row selection circuitrycomprises a hash generator such as the hash generator 2800 configured togenerate a hash value from input data 2810 representing at least aportion of the virtual memory address so that the row is selected independence upon the hash value. As mentioned above, in examplearrangements the index for the DRAM row is a hash (or part of) (VFN,VMID, ASID) and the same goes for the key. The combination of DRAM rowand key should be a unique to a specific tuple (VFN, VMID, ASID).

FIG. 29 schematically illustrates circuitry to write data to the memoryarray providing the DRAM-backed translation data buffer. A write processoccurs in situations such as that represented by the step 2360 of FIG.23, in that, when the translation data for the input virtual memoryaddress is not currently held by the translation data buffer, thecontrol circuitry is configured to store the translation data for theinput virtual memory address, received from the page table accesscircuitry, in the translation data buffer. The arrangement of FIG. 29attends to this writing in the case that the key-value structuredescribed here is used. The circuitry of FIG. 29 comprises a rowselector 2900 using the arrangement of FIG. 28 to select a row andpopulate the row address 2525 in dependence upon the initial memoryaddress or at least a part of it. This provides an example in which, forstorage of translation data in the translation data buffer, the rowselection circuitry is configured to select a row of the array independence upon at least the portion of the initial memory address forthat instance of translation data.

The selected row is moved to the row buffer 2510 for processing. Adetector 2920 detects whether all of the (key, entries) in the selectedrow are occupied and, if so, victim selection and deletion circuitry2930 selects one of the current entries for deletion using a victimselection process such as deleting the oldest of the current entries.Storage circuitry 2940 writes the new (key, value) pair to the rowbuffer 2510 and the row buffer is then copied back into the memory arrayas discussed above.

The example arrangement therefore provides an example of write circuitry2920, 2930, 2940 to store translation data in the selected row, thewrite circuitry comprising: detector circuitry 2920 to detect whetherthe selected row has unused key entries and value entries to store thetranslation data; victim deletion circuitry 2930 to select a key entryand associated value entry in the selected row for overwriting inresponse to a detection by the detector circuitry that the selected rowhas insufficient unused capacity to store the translation data, therebyproviding unused key and value entries and value entries in the selectedrow; and storage circuitry 2940 to store the translation data to theunused key and value entries in the selected row. In examples, thevictim deletion circuitry is configured to select a key entry andassociated value entry according to one or more victim selectioncriteria selected from the list consisting of: a least recently accessedkey value and matching entry. The victim deletion circuitry can activelydelete the key value and matching entry so as to make available emptyspace, or can simply control the overwriting by the new data of theselected data.

This process is represented by the schematic flowchart of FIG. 30, inwhich, at a step 3000 a row is selected according to at least a part ofthe initial or virtual memory address for the translation. At a step3010, the contents of that row are loaded to the row buffer 2510. If, ata step 3020 there is empty space available for a key, value pair in theselected row then control passes to a step 3040. Otherwise, at a step3030, a key, value pair of (victim) is selected for deletion and isdeleted. Then, at a step 3040, the new entry is written to the emptyspace available in the row and at a step 3050, the row is written backto the memory. Note that this write back can be delayed depending on thepolicy of the DRAM controller. However, it will be written back to thestorage array at some point in the future.

FIG. 31 is a schematic flowchart representing a summary methodcomprising:

accessing (at a step 3100) a page table to retrieve translation datadefining an address translation between an initial memory address in aninitial memory address space, and a corresponding output memory addressin an output address space;

storing (at a step 3110), in a translation data buffer having an arrayof storage locations arranged in rows and columns, for a subset of theinitial address space, one or more instances of the translation data;

buffering (at a step 3120) a plurality of entries each to storeinformation from a respective portion of a row of the array; and

comparing (at a step 3130), in response to a key value dependent upon atleast the initial memory address, for comparing the key value withinformation stored in each of at least one key entry (for example, atleast two key entries) of the row buffer, each key entry having anassociated value entry for storing at least a representation of acorresponding output memory address.

If as a result of the comparison at the step 3130, the row does notcontain the requested translation, then control passes to a step 3140 atwhich the “valid” signal is set to indicate “unavailable” is set by thecontroller 2000. Otherwise the method continues as:

identifying (at a step 3150) which of the at least one key entry, ifany, is a matching key entry storing information matching the key value;and

outputting (at a step 3160), when there is a matching key entry, atleast the representation of the output memory address in the value entryassociated with the matching key entry.

In the present application, the words “configured to . . . ” are used tomean that an element of an apparatus has a configuration able to carryout the defined operation. In this context, a “configuration” means anarrangement or manner of interconnection of hardware or software. Forexample, the apparatus may have dedicated hardware which provides thedefined operation, or a processor or other processing device may beprogrammed to perform the function. “Configured to” does not imply thatthe apparatus element needs to be changed in any way in order to providethe defined operation.

Although illustrative embodiments of the invention have been describedin detail herein with reference to the accompanying drawings, it is tobe understood that the invention is not limited to those preciseembodiments, and that various changes, additions and modifications canbe effected therein by one skilled in the art without departing from thescope and spirit of the invention as defined by the appended claims. Forexample, various combinations of the features of the dependent claimscould be made with the features of the independent claims withoutdeparting from the scope of the present invention.

1. An apparatus comprising: an input address port to receive an inputaddress from processor circuitry; address storage to store a translationbetween the input address and an output address in an output addressspace; an output address port to output the output address; an inputdata port to receive data; data storage to store the data in one of aplurality of locations; an output data port to output the data stored inthe data storage; and control circuitry to cause the data storage tostore the translation between the input address and the output address,wherein the control circuitry is adapted to issue a signal to cause apage walk to occur in response to the input address being absent fromthe address storage and the data storage.
 2. An apparatus according toclaim 1, wherein the data storage and the address storage are separatememories.
 3. An apparatus according to claim 1, wherein the data storageand the address storage are different regions within the same memory. 4.An apparatus according to claim 3, wherein the plurality of locationstakes the form of an n-ways set-associative memory; and the controlcircuitry is adapted to cause the data storage to store the translationin one or more repurposed ways of the n-ways.
 5. An apparatus accordingto claim 3, wherein the plurality of locations takes the form of ann-ways set-associative memory; and the control circuitry is adapted tocause the data storage to store the translation in one or morerepurposed sets of the memory.
 6. An apparatus according to claim 1,wherein in response to a request for the translation when thetranslation is absent from the address storage and the data storage, thecontrol circuitry is adapted to issue a signal to cause a page walk tooccur.
 7. An apparatus according to claim 3, comprising: a regionpointer to indicate a border between a region used by the addressstorage and a region used by the data storage.
 8. An apparatus accordingto claim 1, wherein a replacement policy indicates for each of theplurality of locations, a preference for storing a translation comparedto data.
 9. An apparatus according to claim 8, wherein the replacementpolicy is dynamically configurable.
 10. An apparatus according to claim1, wherein the control circuitry is adapted to cause the data storage tostore the translation between the input address and the output addressin dependence on at least one first condition.
 11. An apparatusaccording to claim 10, wherein the first condition is from the listcomprising: a miss rate of the address storage, a hit rate of theaddress storage, an access rate of the address storage, a miss rate ofthe data storage, a hit rate of the data storage, and an access rate ofthe data storage.
 12. An apparatus according to claim 1, wherein thecontrol circuitry is adapted to cause the translation between the inputaddress and the output address to be stored in a part of the datastorage.
 13. An apparatus according to claim 12, wherein a size of thepart is dependent on at least one second condition.
 14. An apparatusaccording to claim 13, wherein the second condition is from the listcomprising: a miss rate of the address storage, a hit rate of theaddress storage, an access rate of the address storage, a miss rate ofthe data storage, a hit rate of the data storage, and an access rate ofthe data storage.
 15. An apparatus according to claim 1, wherein inresponse to a miss on the input address in the address storage, a readrequest is sent to the data storage for the translation.
 16. Anapparatus according to claim 15, wherein the read request is sent to thedata storage in parallel with a page walk request being issued.
 17. Anapparatus according to claim 1, wherein in response to the outputaddress being determined based on an input address, the apparatus isadapted to fetch data stored in the data storage that is associated withthe output address.
 18. A method comprising: receiving an input addressfrom processor circuitry; storing, in address storage, a translationbetween the input address and an output address in an output addressspace; receiving data; storing the data in data storage; causing thedata storage to store the translation between the input address and theoutput address; and in response to the input address being absent fromthe address storage and the data storage, issuing a signal to cause apage walk to occur.
 19. An apparatus comprising: means for receiving aninput address from processor circuitry; means for storing a translationbetween the input address and an output address in an output addressspace; means for receiving data; means for storing the data, wherein themeans for storing the data are made to store the translation between theinput address and the output address; and means for issuing a signal tocause a page walk to occur in response to the input address being absentfrom the address storage and the data storage.